Working with a Shared Source (file-based approach)

The main advantage is the sharing of source and objects files. Just a small part of all source and object files need to reside in the Private Working Environments.

After the creation of the Private Working Environment the whole project is visible for SNiFF+´s browsing and code comprehension tools. Since the Shared Working Environments are read only, it is necessary to check out modules and files to be modified. The checked out files will then reside in the private workspace, all other files will be shared from the Shared Source Working Environments.
Objects files can be shared by using a Shared Object Working Environment (SOWE).

Advantages | Disandvantages
Sharing of source files by using SSWE(s). Complete browsing information for the whole project. Sharing of object files by using SOWE(s). Less compilation time. Modules can be checked out from SNiFF+´s GUI. Automatic creation of the private WE by SNiFF+. | Cvs update should be used for single files only, because it makes all files local; use SNiFF+ update instead, which is slower Higher network bandwidth requirements due to shared source

The typical development cycle when using a shared source is like this:

- Open the project in a PWE. All files are shown from the Shared Source, no files are local. The Shared Source must be CVS-Controlled.
- Browse the files. If a file needs to be edited, execute File > Check out... (with concurrent lock) to get a local copy of the file to be edited.
- Edit the file until you are satisfied; execute CVS > Update File to incorporate any changes made by other developers. Resolve any Conflicts.
- Execute File > Check in File to check in single files or CVS Modules > Commit Module to commit all modifications made in a single step.
- Execute File > Update File or Project > Update Workspace to clean any local copies of files that have already been updated in the Shared Source.

For other special commands, see the following sections.